System and method for configuring a local service control point with a call processor in an architecture

ABSTRACT

A system and method for processing a call comprises a signaling interface to receive and process call signaling and transmit call signaling between a call processor and communication devices such as a local number portability service control point. A call processor processes call signaling to determine call connections. A local service control point (local SCP) provides information such as, for example, for N00 routing and virtual private network (VPN) routing. The local SCP resides with the call processor on a single platform so that they are connected, for example, through a backplane or bus architecture. In this configuration, transaction capabilities application part messages do not have to be transmitted between the signaling interface and the local SCP. Instead, direct communication can occur through control messages transmitted between the local SCP and the call processor thereby realizing increased speed and processing efficiency. Because the local SCP resides with the call processor, two remote dips to an SCP is not necessary.

RELATED APPLICATIONS

This application is a continuation of pending application Ser. No.10/447,002, filed on May 28, 2003, which is a continuation of U.S. Pat.No. 6,597,701, filed on Dec. 22, 1998, which are hereby incorporated byreference into this application.

FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

MICROFICHE APPENDIX

Not Applicable

FIELD OF THE INVENTION

The present invention relates to the field of telecommunications callswitching and transport and, more particularly, for connecting adatabase having call information to a call processor.

BACKGROUND OF THE INVENTION

Broadband systems provide telecommunications providers with manybenefits, including greater bandwidth, more efficient use of bandwidth,and the ability to integrate voice, data, and video communications.These broadband systems provide callers with increased capabilities atlower costs. The broadband systems use call signaling to determine callrouting and processing.

During the call routing and call connection process, switches and othercommunication devices obtain information for call routing and processingfrom service control points (SCPs). These SCPs typically containinformation, such as for N00 routing and local number portability (LNP).The switches and communication devices have to send messages to theSCPs, and the information is returned to the switch or communicationdevice in a message. Typically, the messages are formatted astransaction capabilities application part (TCAP) queries and responses.

However, for a call sometimes several instances of transmitting themessages back and forth between the switch and the SCP occur. Thisincreases the time in which a call can be connected. Thus, there is aneed to connect calls and obtain information at an increased rate andefficiency.

SUMMARY OF THE INVENTION

The present invention comprises a system for processing a call havingcall signaling and user communications. The system comprises a signalingprocessor adapted to receive the call signaling and to process the callsignaling to select a connection for the user communications and totransmit a control message that is not a transaction capabilitiesapplication part message requesting information for use in processingthe call signaling. A local service control point is adapted to receivethe control message, to process the control message to obtain responseinformation, and to provide a response message with the responseinformation to the signaling processor.

The present invention further comprises a system for processing a callhaving call signaling and user communications. The system comprises asignaling processor adapted to receive the call signaling and to processthe call signaling to select a connection for the user communicationsand to transmit a control message requesting information for use inprocessing the call signaling. A local service control point isconnected to the signaling processor in a single computer architectureand is adapted to receive the control message, to process the controlmessage to obtain response information, and to provide a responsemessage with the response information to the signaling processor.

The present invention further is directed to a system for processing acall having call signaling and user communications. The system comprisesa signaling interface that is adapted to receive and process the callsignaling to determine call information elements and to transmit thecall information elements. A call processor is adapted to receive thecall information elements from the signaling interface, to process thecall information elements to determine a connection for the usercommunications and to transmit a control message that is not atransaction capabilities application part message requesting informationfor use in processing the call signaling. A local service control pointis adapted to receive the control message, to process the controlmessage to obtain response information, and to provide a responsemessage with the response information to the signaling processor.

Still further, the present invention is directed to a system forprocessing a call having call signaling and user communications. Thesystem comprises a signaling interface that is adapted to receive andprocess the call signaling to determine call information elements and totransmit the call information elements. A call processor is adapted toreceive the call information elements from the signaling interface, toprocess the call information elements to determine a connection for theuser communications and to transmit a control message that is not atransaction capabilities application part message requesting informationfor use in processing the call signaling. A local service control pointis connected to the signaling processor in a single computerarchitecture and is adapted to receive the control message, to processthe control message to obtain response information, and to provide aresponse message with the response information to the signalingprocessor.

Further yet, the present invention is directed to a method forprocessing a call having call signaling and user communications. Themethod comprises receiving and processing the call signaling in asignaling processor to determine a connection for the usercommunications. A request for information for use in processing the callsignaling is transmitted to a local service control point in a controlmessage that is not a transaction capabilities application part querymessage. The method further comprises receiving and processing thecontrol message to obtain response information. The response informationis provided in a response message that is not a transaction capabilitiesapplication part response message.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a call processing system in accordance withan embodiment of the present invention.

FIG. 2 is a block diagram of an expanded call processing system inaccordance with an embodiment of the present invention.

FIG. 3 is a block diagram of an expanded call processing system inaccordance with an embodiment of the present invention.

FIG. 4 is a functional diagram of a controllable asynchronous transfermode matrix in accordance with the present invention.

FIG. 5 is a functional diagram of a controllable asynchronous transfermode matrix with time division multiplex capability in accordance withthe present invention.

FIG. 6 is a functional diagram of an asynchronous transfer modeinterworking unit for use with a synchronous optical network system inaccordance with the present invention.

FIG. 7 is a functional diagram of an asynchronous transfer modeinterworking unit for use with a synchronous digital hierarchy system inaccordance with the present invention.

FIG. 8 is a block diagram of a signaling processor constructed inaccordance with the present system.

FIG. 9 is a block diagram of a data structure having tables that areused in the signaling processor of FIG. 8.

FIG. 10 is a block diagram of additional tables that are used in thesignaling processor of FIG. 8.

FIG. 11 is a block diagram of additional tables that are used in thesignaling processor of FIG. 8.

FIG. 12 is a block diagram of additional tables that are used in thesignaling processor of FIG. 8.

FIG. 13 is a table diagram of a time division multiplex trunk circuittable used in the signaling processor of FIG. 8.

FIG. 14 is a table diagram of an asynchronous transfer mode trunkcircuit table used in the signaling processor of FIG. 8.

FIG. 15A is a table diagram of a trunk group table used in the signalingprocessor of FIG. 8.

FIG. 15B is a continuation table diagram of the trunk group table ofFIG. 15A.

FIG. 15C is a continuation table diagram of the trunk group table ofFIG. 15B.

FIG. 16 is a table diagram of a carrier table used in the signalingprocessor of FIG. 8.

FIG. 17 is a table diagram of an exception table used in the signalingprocessor of FIG. 8.

FIG. 18 is a table diagram of an originating line information table usedin the signaling processor of FIG. 8.

FIG. 19 is a table diagram of an automated number identification tableused in the signaling processor of FIG. 8.

FIG. 20 is a table diagram of a called number screening table used inthe signaling processor of FIG. 8.

FIG. 21 is a table diagram of a called number table used in thesignaling processor of FIG. 8.

FIG. 22 is a table diagram of a day of year table used in the signalingprocessor of FIG. 8.

FIG. 23 is a table diagram of a day of week table used in the signalingprocessor of FIG. 8.

FIG. 24 is a table diagram of a time of day table used in the signalingprocessor of FIG. 8.

FIG. 25 is a table diagram of a time zone table used in the signalingprocessor of FIG. 8.

FIG. 26 is a table diagram of a routing table used in the signalingprocessor of FIG. 8.

FIG. 27 is a table diagram of a trunk group class of service table usedin the signaling processor of FIG. 8.

FIG. 28 is a table diagram of a treatment table used in the signalingprocessor of FIG. 8.

FIG. 29 is a table diagram of an outgoing release table used in thesignaling processor of FIG. 8.

FIG. 30 is a table diagram of a percent control table used in thesignaling processor of FIG. 8.

FIG. 31 is a table diagram of a call rate table used in the signalingprocessor of FIG. 8.

FIG. 32 is a table diagram of a database services table used in thesignaling processor of FIG. 8.

FIG. 33A is a table diagram of a signaling connection control part tableused in the signaling processor of FIG. 8.

FIG. 33B is a continuation table diagram of the signaling connectioncontrol part table of FIG. 33A.

FIG. 33C is a continuation table diagram of the signaling connectioncontrol part table of FIG. 33B.

FIG. 33D is a continuation table diagram of the signaling connectioncontrol part table of FIG. 33C.

FIG. 34 is a table diagram of an intermediate signaling networkidentification table used in the signaling processor of FIG. 8.

FIG. 35 is a table diagram of a transaction capabilities applicationpart table used in the signaling processor of FIG. 8.

FIG. 36 is a table diagram of a external echo canceller table used inthe signaling processor of FIG. 8.

FIG. 37 is a table diagram of an interworking unit used in the signalingprocessor of FIG. 8.

FIG. 38 is a table diagram of a controllable asynchronous transfer modematrix interface table used in the signaling processor of FIG. 8.

FIG. 39 is a table diagram of a controllable asynchronous transfer modematrix table used in the signaling processor of FIG. 8.

FIG. 40A is a table diagram of a site office table used in the signalingprocessor of FIG. 8.

FIG. 40B is a continuation table diagram of the site office table ofFIG. 40A.

FIG. 40C is a continuation table diagram of the site office table ofFIG. 40B.

FIG. 40D is a continuation table diagram of the site office table ofFIG. 40C.

FIG. 41A is a table diagram of an advanced intelligent network eventparameters table used in the signaling processor of FIG. 8.

FIG. 41B is a continuation table diagram of the advanced intelligentnetwork event parameters table of FIG. 41A.

FIG. 42 is a table diagram of a message mapping table used in thesignaling processor of FIG. 8.

DETAILED DESCRIPTION

Telecommunication systems have a number of communication devices inlocal exchange and interexchange environments that interact to providecall services to customers. Both traditional and intelligent network(IN) services and resources are used to process, route, or connect acall to a designated connection.

These systems typically obtain information from service control points(SCPs) to assist in routing and processing of calls. When a switch orcommunication device requires information from the SCP, it sends atransaction capabilities application part (TCAP) query message to theSCP. The SCP responds with a TCAP response. The TCAP response containsthe requested information if that information is available.

In addition, new technologies have been implemented to process callsthat are to be ported for local number portability (LNP). For calls thatrequire LNP processing or routing, two TCAP queries and two TCAPresponses can be required. In a first method, a first query to an SCPrequests information for the call for routing and processing. Theresponse may contain information which allows the switch orcommunication device to determine that the called number is a portednumber. Then, a second TCAP query is generated to an LNP SCP to obtainthe destination for the ported number.

In a second method, a first query to an SCP requests information for thecall for routing and processing. The SCP may determine that the numberis ported and initiate a TCAP query to an LNP SCP. The LNP SCP respondswith the ported number to the first SCP. The first SCP then responds tothe switch or communication device with the information.

However, in the first method, the switch or communication device mustgenerate two TCAP queries and process two TCAP responses. This processis time consuming and processing intensive.

In the second method, two TCAP queries and two TCAP responses still areprocessed. However, in the second method, the first SCP must havesignificant processing capacity. Not only is this process timeconsuming, but also the first SCP is unlikely to be able to process theincreased load of generating and processing the increased TCAPs frommultiple carries such as from both local exchange carriers (LECs) andinterexchange carriers (IXCs) for all feature group access.

Moreover, in the second method the response from the first SCP to theswitch or communication device would have to relay two pieces ofinformation: first it must identify that the first SCP queried the LNPSCP for the ported number, and second it must specify that the responseto the switch or communications device contains the ported number.Otherwise, without knowing this information, the switch or communicationdevice would have to initiate a query to the LNP SCP requesting theported number, thus completing double the work necessary to process thecall. Unfortunately, many responses from the first SCP to the switch orcall processor may not contain these two required pieces of information.

The increase in TCAP queries and required responses for general queriesto the SCP, as well as for calls that are ported, places an increasedamount of traffic on the SCPs which can overload the SCPs. In addition,processing of the queries can take an extended time, more than the timeallowed for call connections.

The present invention provides a system and method that increases thespeed of call processing by placing the SCP functionality with thesignaling processor. Functionally, the SCP becomes the local node SCPdatabase and can be configured to use legacy system data feeds. Thisallows the signaling processor to obtain information from the SCPwithout initiating a TCAP query. In addition, because the system can beconfigured in a bus-type architecture, information can be obtained muchquicker without the need to interface with multiple components.

The system of the present invention processes call information to makecall connections. A call has user communications and call signaling. Theuser communications contain the caller's information, such as a voicecommunication or data communication, and they are transported over aconnection. Call signaling contains information that facilitates callprocessing, and it is communicated over a link. Call signaling, forexample, contains information describing the called number and thecalling number. Examples of call signaling are standardized signaling,such as signaling system #7 (SS7), C7, integrated services digitalnetwork (ISDN), and digital private network signaling system (DPNSS),which are based on flu recommendation Q.933. A call can be connected toand from communication devices.

Connections are used to transport user communications and other deviceinformation between communication devices and between the elements anddevices of the system. The term “connection” as used herein means thetransmission media used to carry user communications between elements ofthe various telecommunications networks and systems. For example, aconnection could carry a user's voice, computer data, or othercommunication device data. A connection can be associated with eitherin-band communications or out-of-band communications.

Links are used to transport call signaling and control messages. Theterm “link” as used herein means a transmission media used to carry callsignaling and control messages. For example, a link would carry callsignaling or a device control message containing device instructions anddata. A link can carry, for example, out-of-band signaling such as thatused in SS7, C7, ISDN, DPNSS, B-ISDN, GR-303, or could be via local areanetwork (LAN), or data bus call signaling. A link can be, for example,an asynchronous transfer mode (ATM) adaptation layer 5 (AAL5) data link,UDP/IP, ethernet, DS0, or DS1. In addition, a link, as shown in thefigures, can represent a single physical link or multiple links, such asone link or a combination of links of ISDN, SS7, TCP/IP, or some otherdata link. The term “control message” as used herein means a control orsignaling message, a control or signaling instruction, or a control orsignaling signal, whether proprietary or standardized, that conveysinformation from one point to another.

FIG. 1 illustrates an exemplary embodiment of a call processing system102 of the present invention. The call processing system 102 comprises anon-local service control point (SCP), such as a local numberportability (LNP) SCP 104, linked to a call connection system 106 havinga signaling processor 108 linked to a local service control point (localSCP) 110.

The LNP SCP 104 contains customer data including information fortelecommunication services available to a customer such as local numberportability. The LNP SCP 104 has tables identifying ported numbers foreach number plan area-number (NPA-NXX). The LNP SCP 104 receives,analyzes, and responds to TCAP messages formatted as described in theBellcore AIN 0.1 reference and its updates, the contents of which areincorporated herein by reference.

The signaling processor 108 is a signaling platform that can receive,process, and generate call signaling. Based on the processed callsignaling, the signaling processor 108 selects processing options,services, or resources for the user communications and generates andtransmits control messages that identify the communication device,processing option, service, or resource that is to be used. Thesignaling processor 108 also selects virtual connections andcircuit-based connections for call routing and generates and transportscontrol messages that identify the selected connections. The signalingprocessor 108 can process various forms of signaling, including ISDN,GR-303, B-ISDN, SS7, and C7. A preferred signaling processor isdiscussed below.

The local SCP 110 contains information about the system and how to routecalls through the system. The local SCP 110 is queried from thesignaling processor 108 to determine how to route calls with advancedrouting features such as N00 routing, routing menu, or virtual privatenetwork (VPN) routing.

The signaling processor 108 and the local SCP 110 can be located on thesame platform and connected by a single architecture, such as abackplane, a bus architecture, or in a single computer. For example, thesignaling processor 108 and the local SCP 110 can be on a singlemotherboard with programmed processor chips. With either structure,increased processing speed and efficiency is obtained. An interfacebetween the two components is not required such that a TCAP query is notrequired to be generated between the signaling processor 108 and thelocal SCP 110. In addition, a TCAP response is not required to begenerated between the local SCP 110 and the signaling processor 108.Information can be transferred between the two components quickly andeasily without having to build messages to be transmitted to devicesoutside of the local SCP 110 and signaling processor 108 architecture.

The call processing system of FIG. 1 operates as follows. In a firstexample, the signaling processor 108 receives call processing from acommunication device (not shown). The signaling processor 108 processesthe call signaling and determines that information is required from thelocal SCP 110. In this example, the called number is an 800 number thatrequires translation to a ten digit NPA-NXX number. The signalingprocessor 108 passes a control message to the local SCP 110 requestingthe information. The control message is not a TCAP message and thereforeis not required to be formatted through an SS7 stack. In this example,the control message is transmitted to the local SCP 110 through a bus.

The local SCP 110 receives the control message from the signalingprocessor 108 and processes the control message. The local SCP 110responds to the signaling processor 108 with the requested information.In this example, the local SCP 110 responds with a ten digit translatedcalled number. The response is a control message that is sent from thelocal SCP 110 to the signaling processor 108. The response is not a TCAPresponse and therefore is not required to be formatted through an SS7stack. In this example, the control message is transmitted from thelocal SCP 110 to the signaling processor 108 through a bus.

In another example, the signaling processor 108 receives call processingfrom a communication device (not shown). The signaling processor 108processes the call signaling and determines that information is requiredfrom the local SCP 110. In this example, the called number is an 800number that requires translation to a ten digit NPA-NXX number. Thesignaling processor 108 passes a control message to the local SCP 110requesting the information.

The local SCP 110 receives the control message from the signalingprocessor 108 and processes the control message to obtain responseinformation. The response information may contain the requestedinformation, or it may specify that the requested information is notavailable or unknown. The local SCP 110 responds to the signalingprocessor 108 with the response information. In this example, the localSCP 110 responds with a ten digit translation to obtain the translatedcalled number.

The signaling processor 108 processes the information that is receivedfrom the local SCP 110 to determine if the NPA-NXX of the ten digitnumber has been flagged as a ported number. If the signaling processor108 determines that the number has been flagged as a ported number, itinitiates a TCAP query to the LNP SCP 104.

The LNP SCP 104 receives the TCAP query and processes it. If the LNP SCP104 determines that the number is a ported number, it transmits alocation routing number (LRN) to the signaling processor 108 in a TCAPresponse message. If the LNP SCP 104 determines that the number is not aported number, it transmits the ten digit translated called number backto the signaling processor 108 in the response message.

FIG. 2 illustrates an example of an expanded call processing system102A. The call processing system 102A comprises, in addition to the LNPSCP 104 and the local SCP 110 of FIG. 1, a signaling interface 202, acall processor 204, and a call process and control system (CPCS) 206.

The signaling interface 202 receives, processes, and transmits callsignaling. The signaling interface 202 can obtain information from, andtransmit information to, a communication device. Such information may betransferred, for example, as a TCAP message in queries or responses oras other SS7 messages such as an initial address message (IAM). Thesignaling interface 202 also passes information to the call processor204 for processing and passes information from the call processor toother communication devices (not shown).

The call processor 204 is a signaling platform that can receive andprocess call signaling. The call processor 204 has data tables whichhave call connection data and which are used to process the callsignaling. Based on the processed call signaling, the call processor 204selects processing options, services, resources, or connections for theuser communications. The call processor 204 generates and transmitscontrol messages that identify the communication device, processingoption, service, or resource that is to receive call signaling or thatis be used in call connections or further call processing. The callprocessor 204 also selects virtual connections and circuit-basedconnections for routing of call signaling and connections for usercommunications and generates and transports control messages thatidentify the selected connections.

The CPCS 206 is a management and administration system. The CPCS 206 isthe user interface and external systems interface into the callprocessor 204. The CPCS 206 serves as a collection point forcall-associated data such as translations having call routing data,logs, operational measurement data, alarms, statistical information,accounting information, and other call data. The CPCS 206 accepts data,such as the translations, from operations systems and updates the datain the tables in the call processor 204. The CPCS 206 also providesconfiguration data to the elements of the call processing system 102Aincluding to the signaling interface 202, the call processor 204, andany interworking units (not shown) or any controllable ATM matrixdevices (not shown). In addition, the CPCS 206 provides for remotecontrol of call monitoring and call tapping applications from the callprocessor 204. The CPCS 206 may be a local CPCS that services onlycomponents of a local call processing system or a regional CPCS thatservices components of multiple call processing systems.

The call processor 204 and the local SCP 110 can be located on the sameplatform and connected by a backplane or bus architecture. In addition,the signaling processor 108 and the local SCP 110 can be on a singlemotherboard with programmed processor chips. Alternately, the signalinginterface 202 can be combined with the call processor 204 and the localSCP 110 in either configuration.

With any herein described structure, increased processing speed andefficiency is obtained. Cross office time limits can be maintained. Thatis, for example, the time that it takes the call processor 204 toprocess a call from the originating side to the terminating side so thata connection can be made, including the time to get information fromcomponents such as the local SCP 110 can be maintained within therequired time limits.

Moreover, an interface between the components is not required such thata TCAP query is not required to be generated from the call processor204, through the signaling interface 202, and to the local SCP 110. Inaddition, a TCAP response is not required to be generated from the localSCP 110, through the signaling interface 202, and to the call processor204. Because the components may be configured to transfer information,messages, or communications with and between the other components in anyformat, standard, or method, communications between the components canoccur at a faster rate and in a more efficient manner. Information canbe transferred between the components quickly and easily without havingto build messages to be transmitted to devices outside of the local SCP110 and call processor 204, and optionally the signaling interface 202,architecture.

The operation of the call processing system 102A of FIG. 2 will bedescribed below with reference to a call connection with usercommunications. This will provide a more complete description of theoperation of the call processing system 102A when used with usercommunication connection devices. It will be appreciated that the wholeof the call processing system with the user communication devices, i.e.an interworking unit and an ATM matrix, for a total call connection isan aspect of the present invention.

FIG. 3 illustrates a call processing system 102B for call connection. Inaddition to the devices of FIG. 2, the call processing system 102B ofFIG. 3 comprises an interworking unit 302 connected to an ATM matrix 304by a connection 306, each of which is linked to the call processor 204and the CPCS 206. A first communication device 308 and a secondcommunication device 310 are connected to the system through connections312 and 314, respectively, and links.

The interworking unit 302 interworks traffic between various protocols.Preferably, the interworking unit 302 interworks between ATM traffic andnon-ATM traffic. The interworking unit 302 operates in accordance withcontrol messages received from the call processor 204. These controlmessages typically are provided on a call-by-call basis and typicallyidentify an assignment between a DS0 and a VP/VC for which usercommunications are interworked. In some instances, the interworking unit302 may transport control messages which may include data to the callprocessor 204.

The ATM matrix 304 is a controllable ATM matrix that establishesconnections in response to control messages received from the callprocessor 204. The ATM matrix 304 is able to interwork between ATMconnections and time division multiplex (TDM) connections. The ATMmatrix 304 also cross connects ATM connections with other ATMconnections. In addition, the ATM matrix 304 can switch calls from TDMconnections to other TDM connections. The ATM matrix 304 transmits andreceives call signaling and user communications over the connections.

The communication devices 308 and 310 comprise customer premisesequipment (CPE), a service platform, a switch, a remote digitalterminal, a cross connect, an interworking unit, an ATM gateway, or anyother device capable of initiating, handling, or terminating a call. CPEcan be, for example, a telephone, a computer, a facsimile machine, or aprivate branch exchange. A service platform can be, for example, anyenhanced computer platform that is capable of processing calls. A remotedigital terminal is a device that concentrates analog twisted pairs fromtelephones and other like devices and converts the analog signals to adigital format known as GR-303. An ATM gateway is a device that changesATM cell header VP/VC identifiers. The communication devices 308 and 310may be TDM based or ATM based. In the system of FIG. 3, preferably thefirst communication device 308 is TDM based, and the secondcommunication device 310 is ATM based.

In an example of the operation of the signaling system 102B, the firstcommunication device 308 transports user communications and callsignaling. The signaling interface 202 receives the call signaling, andthe interworking unit 302 receives the user communications.

The signaling interface 202 processes the call signaling and converts itto call information elements, such as message parameters, that can beprocessed by the call processor 204. A call information element may be,for example, an integrated services user part initial address message(ISUP IAM) message parameter from an MSU or other message parameters.The signaling interface 202 passes the message parameters to the callprocessor 204.

The call processor 204 processes the call signaling message parametersand determines that information is required from the local SCP 110 tocomplete call processing. In this example, the call is a VPN call.

The call processor 204 passes a control message to the local SCP 110requesting the information. The control message is not a TCAP messageand therefore is not required to be formatted through an SS7 stack. Inthis example, the control message is transmitted to the local SCP 110through a backplane.

The local SCP 110 receives the control message from the call processor204 and processes the control message to obtain the responseinformation. The response information may contain the requestedinformation, or it may specify that the requested information is notavailable or unknown.

The local SCP 110 responds to the call processor 204 with the responseinformation. In this example, the local SCP 110 responds with a routingcode. The response is a control message that is sent from the local SCP110 to the call processor 204. The response is not a TCAP response andtherefore is not required to be formatted through an SS7 stack. In thisexample, the control message is transmitted from the local SCP 110 tothe call processor 204 through a backplane.

The call processor 204 receives and processes the information from thelocal SCP 110. The call processor 204 determines that the call is to beconnected to the second communication device 310. In this example, thesecond communication device is an ATM device.

The call processor 204 selects a connection, such as a VP/VC on theconnection 304, over which the user communications will be transmittedbetween the interworking unit 302 and the ATM matrix 304 and aconnection, such as a VP/VC on the connection 314, over which the usercommunications will be transmitted between the ATM matrix and the secondcommunication device 310.

The call processor 204 transmits a control message to each of theinterworking unit 302 and the ATM matrix 304 identifying the selectedconnections 306 and 314. In addition, the call processor 204 transmitsthe required call signaling to the signaling interface 202 to beconfigured for transmission as, for example, an SS7 message.

The interworking unit 302 receives the user communications from thefirst communication device 308 and the control message from the callprocessor 204. In response to the control message, the interworking unit302 interworks the user communications to the designated connection 306.

The ATM matrix 304 receives the user communications from theinterworking unit 302 and the control message from the call processor204. In response to the control message, the ATM matrix 304 connects theuser communications over the designated connection 314 to the secondcommunication device 310.

In another example, the first communication device 308 transports usercommunications and call signaling. The signaling interface 202 receivesthe call signaling, and the interworking unit 302 receives the usercommunications.

The signaling interface 202 processes the call signaling and converts itto call information elements, such as message parameters, that can beprocessed by the call processor 204. The signaling interface 202 passesthe message parameters to the call processor 204.

The call processor 204 processes the call signaling message parametersand determines that information is required from the local SCP 110 tocomplete call processing. In this example, the called number is an N00number that requires translation to a ten digit NPA-NXX number.

The call processor 204 passes a control message to the local SCP 110requesting the information. The control message is not a TCAP messageand therefore is not required to be formatted through an SS7 stack. Inthis example, the control message is transmitted to the local SCP 110through a backplane.

The local SCP 110 receives the control message from the call processor204 and processes the control message to obtain the responseinformation. The response information may contain the requestedinformation, or it may specify that the requested information is notavailable or unknown.

The local SCP 110 responds to the call processor 204 with the responseinformation. In this example, the local SCP 110 responds with a tendigit translated called number. The response is a control message thatis sent from the local SCP 110 to the call processor 204. The responseis not a TCAP response and therefore is not required to be formattedthrough an SS7 stack. In this example, the control message istransmitted from the local SCP 110 to the call processor 204 through abackplane.

The call processor 204 receives and processes the information from thelocal SCP 110. The call processor 204 processes the information that isreceived from the local SCP 110 to determine if the NPA-NXX of the tendigit translated called number has been flagged as a ported number. Ifthe call processor 204 determines that the number has been flagged as aported number, it initiates a TCAP query by transmitting call messageparameters to the signaling interface 202. Otherwise processingcontinues as normal.

The signaling interface 202 receives the message parameters from thecall processor 204 and builds, for example, an AIN 0.1 SCP TCAP query.The signaling interface 202 transmits the TCAP query to the LNP SCP 104.

The LNP SCP 104 receives the TCAP query and processes it. If the LNP SCP104 determines that the number is a ported number, it transmits an LRNto the signaling interface 202 in, for example, an AIN 0.1 TCAP responsemessage. If the LNP SCP 104 determines that the number is not a portednumber, it transmits the ten digit translated called number back to thesignaling interface 202 in the response message.

The signaling interface 202 receives the TCAP response and processes itto obtain the message parameters. The signaling interface 202 transmitsthe message parameters to the call processor 204.

The call processor 204 receives and processes the message parameters anddetermines that the call is to be connected to the second communicationdevice 310. In this example, the second communication device 310 is anATM device.

The call processor 204 selects a connection, such as a VP/VC on theconnection 304, over which the user communications will be transmittedbetween the interworking unit 302 and the ATM matrix 304 and aconnection, such as a VP/VC on the connection 314, over which the usercommunications will be transmitted between the ATM matrix and the secondcommunication device 310.

The call processor 204 transmits a control message to each of theinterworking unit 302 and the ATM matrix 304 identifying the selectedconnections 306 and 314. In addition, the call processor 204 transmitsthe required call signaling to the signaling interface 202 to beconfigured for transmission.

The interworking unit 302 receives the user communications from thefirst communication device 308 and the control message from the callprocessor 204. In response to the control message, the interworking unit302 interworks the user communications to the designated connection 306.

The ATM matrix 304 receives the user communications from theinterworking unit 302 and the control message from the call processor204. In response to the control message, the ATM matrix 304 connects theuser communications over the designated connection 314 to the secondcommunication device 310.

The Controllable ATM Matrix

FIG. 4 illustrates an exemplary embodiment of a controllableasynchronous transfer mode (ATM) matrix (CAM), but other CAMs thatsupport the requirements of the invention also are applicable. The CAM402 may receive and transmit ATM formatted user communications or callsignaling.

The CAM 402 preferably has a control interface 404, a controllable ATMmatrix 406, an optical carrier-M/synchronous transport signal-M(OC-M/STS-M) interface 408, and an OC-X/STS-X interface 410. As usedherein in conjunction with OC or STS, “M” refers to an integer, and “X”refers to an integer.

The control interface 404 receives control messages originating from thesignaling processor 412, identifies virtual connection assignments inthe control messages, and provides these assignments to the matrix 406for implementation. The control messages may be received over an ATMvirtual connection and through either the OC-M/STS-M interface 408 orthe OC-X/STS-X interface 410 through the matrix 406 to the controlinterface 404, through either the OC-M/STS-M interface or the OC-X/STS-Xinterface directly to the control interface, or through the controlinterface from a link.

The matrix 406 is a controllable ATM matrix that provides cross connectfunctionality in response to control messages from the signalingprocessor 412. The matrix 406 has access to virtual path/virtualchannels (VP/VCs) over which it can connect calls. For example, a callcan come in over a VP/VC through the OC-M/STS-M interface 408 and beconnected through the matrix 406 over a VP/VC through the OC-X/STS-Xinterface 410 in response to a control message received by the signalingprocessor 412 through the control interface 404. Alternately, a call canbe connected in the opposite direction. In addition, the a call can bereceived over a VP/VC through the OC-M/STS-M interface 408 or theOC-X/STS-X interface 410 and be connected through the matrix 406 to adifferent VP/VC on the same OC-M/STS-M interface or the same OC-X/STS-Xinterface.

The OC-M/STS-M interface 408 is operational to receive ATM cells fromthe matrix 406 and to transmit the ATM cells over a connection to thecommunication device 414. The OC-M/STS-M interface 408 also may receiveATM cells in the OC or STS format and transmit them to the matrix 406.

The OC-X/STS-X interface 410 is operational to receive ATM cells fromthe matrix 406 and to transmit the ATM cells over a connection to thecommunication device 416. The OC-X/STS-X interface 410 also may receiveATM cells in the OC or STS format and transmit them to the matrix 406.

Call signaling may be received through and transferred from theOC-M/STS-M interface 408. Also, call signaling may be received, throughand transferred from the OC-X/STS-X interface 410. The call signalingmay be connected on a connection or transmitted to the control interfacedirectly or via the matrix 406.

The signaling processor 412 is configured to send control messages tothe CAM 402 to implement particular features on particular VP/VCcircuits. Alternatively, lookup tables may be used to implementparticular features for particular VP/VCs.

FIG. 5 illustrates another exemplary embodiment of a CAM which has timedivision multiplex (TDM) capability, but other CAMs that support therequirements of the invention also are applicable. The CAM 502 mayreceive and transmit in-band and out-of-band signaled calls.

The CAM 502 preferably has a control interface 504, an OC-N/STS-Ninterface 506, a digital signal level 3 (DS3) interface 508, a DS1interface 510, a DS0 interface 512, an ATM adaptation layer (AAL) 514, acontrollable ATM matrix 516, an OC-M/STS-M interface 518A, an OC-X/STS-Xinterface 518B, and an ISDN/GR-303 interface 520. As used herein inconjunction with OC or STS, “N” refers to an integer, “M” refers to aninteger, and “X” refers to an integer.

The control interface 504 receives control messages originating from thesignaling processor 522, identifies DS0 and virtual connectionassignments in the control messages, and provides these assignments tothe AAL 514 or the matrix 516 for implementation. The control messagesmay be received over an ATM virtual connection and through theOC-M/STS-M interface 518A to the control interface 504, through theOC-X/STS-X interface 518B and the matrix 516 to the control interface,or directly through the control interface from a link.

The OC-N/STS-N interface 506, the DS3 interface 508, the DS1 interface510, the DS0 interface 512, and the ISDN/GR-303 interface 520 each canreceive user communications from a communication device 524. Likewise,the OC-M/STS-M interface 518A and the OC-X/STS-X interface 518B canreceive user communications from the communication devices 526 and 528.

The OC-N/STS-N interface 506 receives OC-N formatted user 0ocommunications and STS-N formatted user communications and converts theuser communications to the DS3 format. The DS3 interface 508 receivesuser communications in the DS3 format and converts the usercommunications to the DS1 format. The DS3 interface 508 can receive DS3sfrom the OC-N/STS-N interface 506 or from an external connection. TheDS1 interface 510 receives the user communications in the DS1 format andconverts the user communications to the DS0 format. The DS1 interface510 receives DS1s from the DS3 interface 508 or from an externalconnection. The DS0 interface 512 receives user communications in theDS0 format and provides an interface to the AAL 514. The ISDN/GR-303interface 520 receives user communications in either the ISDN format orthe GR-303 format and converts the user communications to the DS0format. In addition, each interface may transmit user communications inlike manner to the communication device 524.

The OC-M/STS-M interface 518A is operational to receive ATM cells fromthe AAL 514 or from the matrix 516 and to transmit the ATM cells over aconnection to the communication device 526. The OC-M/STS-M interface518A also may receive ATM cells in the OC or STS format and transmitthem to the AAL 514 or to the matrix 516.

The OC-X/STS-X interface 518B is operational to receive ATM cells fromthe AAL 514 or from the matrix 516 and to transmit the ATM cells over aconnection to the communication device 528. The OC-X/STS-X interface518B also may receive ATM cells in the OC or STS format and transmitthem to the AAL 514 or to the matrix 516.

Call signaling may be received through and transferred from theOC-N/STS-N interface 506 and the ISDN/GR-303 interface 520. Also, callsignaling may be received through and transferred from the OC-M/STS-Minterface 518A and the OC-X/STS-X interface 518B. The call signaling maybe connected on a connection or transmitted to the control interfacedirectly or via an interface as explained above.

The AAL 514 comprises both a convergence sublayer and a segmentation andreassembly (SAR) sublayer. The AAL 514 obtains the identity of the DS0and the ATM VP/VC from the control interface 504. The AAL 514 isoperational to convert between the DS0 format and the ATM format. AALsare known in the art, and information about AALs is provided byInternational Telecommunications Union (ITU) documents in the series ofL363, which are incorporated herein by reference. For example, ITUdocument I.363.1 discusses AAL1. An AAL for voice calls is described inU.S. Pat. No. 5,806,553 entitled “Cell Processing for VoiceTransmission,” which is incorporated herein by reference.

Calls with multiple 64 Kilo-bits per second (Kbps) DS0s are known asNx64 calls. If desired, the AAL 514 can be configured to accept controlmessages through the control interface 504 for Nx64 calls. The CAM 502is able to interwork, multiplex, and demultiplex for multiple DS0s. Atechnique for processing VP/VCs is disclosed in U.S. patent applicationSer. No. 08/653,852, which was filed on May 28, 1996, and entitled“Telecommunications System with a Connection Processing System,” andwhich is incorporated herein by reference.

DS0 connections are bi-directional and ATM connections are typicallyuni-directional. As a result, two virtual connections in opposingdirections typically will be required for each DS0. Those skilled in theart will appreciate how this can be accomplished in the context of theinvention. For example, the cross-connect can be provisioned with asecond set of VP/VCs in the opposite direction as the original set ofVP/VCs.

The matrix 516 is a controllable ATM matrix that provides cross connectfunctionality in response to control messages from the signalingprocessor 522. The matrix 516 has access to VP/VCs over which it canconnect calls. For example, a call can come in over a VP/VC through theOC-M/STS-M interface 518A and be connected through the matrix 516 over aVP/VC through the OC-X/STS-X interface 518B in response to a controlmessage received by the signaling processor 522 through the controlinterface 504. Alternately, the Matrix 516 may transmit a call receivedover a VP/VC through the OC-M/STS-M interface 518A to the AAL 514 inresponse to a control message received by the signaling processor 522through the control interface 504. Communications also may occur inopposite directions through the various interfaces.

In some embodiments, it may be desirable to incorporate digital signalprocessing capabilities at, for example, the DS0 level. It also may bedesired to apply echo control to selected DS0 circuits. In theseembodiments, a signal processor may be included. The signaling processor522 is configured to send control messages to the CAM 502 to implementparticular features on particular DS0 or VP/VC circuits. Alternatively,lookup tables may be used to implement particular features forparticular circuits or VP/VCs.

It will be appreciated from the teachings above for the CAMs and for theteachings below for the ATM interworking units, that the above describedCAMs can be adapted for modification to transmit and receive otherformatted communications such as synchronous transport module (STM) andEuropean level (E) communications. For example, the OC/STS, DS3, DS1,DS0, and ISDN/GR-303 interfaces can be replaced by STMelectrical/optical (E/O), E3, E1, E0, and digital private networksignaling system (DPNSS) interfaces, respectively.

The ATM Interworking Unit

FIG. 6 illustrates an exemplary embodiment of an interworking unit whichis an ATM interworking unit 602 suitable for the present invention foruse with a SONET system. Other interworking units that support therequirements of the invention also are applicable. The ATM interworkingunit 602 may receive and transmit in-band and out-of-band calls.

The ATM interworking unit 602 preferably has a control interface 604, anOC-N/STS-N interface 606, a DS3 interface 608, a DS1 interface 610, aDS0 interface 612, a signal processor 614, an AAL 616, an OC-M/STS-Minterface 618, and an ISDN/GR-303 interface 620. As used herein inconjunction with OC or STS, “N” refers to an integer, and “M” refers toan integer.

The control interface 604 receives control messages originating from thesignaling processor 622, identifies DS0 and virtual connectionassignments in the control messages, and provides these assignments tothe AAL 616 for implementation. The control messages are received overan ATM virtual connection and through the OC-M/STS-M interface 618 tothe control interface 604 or directly through the control interface froma link.

The OC-N/STS-N interface 606, the DS3 interface 608, the DS1 interface610, the DS0 interface 612, and the ISDN/GR-303 interface 620 each canreceive user communications from a communication device 624. Likewise,the OC-M/STS-M interface 618 can receive user communications from acommunication device 626.

The OC-N/STS-N interface 606 receives OC-N formatted user communicationsand STS-N formatted user communications and demultiplexes the usercommunications to the DS3 format. The DS3 interface 608 receives usercommunications in the DS3 format and demultiplexes the usercommunications to the DS1 format. The DS3 interface 608 can receive DS3sfrom the OC-N/STS-N interface 606 or from an external connection. TheDS1 interface 610 receives the user communications in the DS1 format anddemultiplexes the user communications to the DS0 format. The DS1interface 610 receives DS1s from the DS3 interface 608 or from anexternal connection. The DS0 interface 612 receives user communicationsin the DS0 format and provides an interface to the AAL 616. TheISDN/GR-303 interface 620 receives user communications in either theISDN format or the GR-303 format and converts the user communications tothe DS0 format. In addition, each interface may transmit usercommunications in like manner to the communication device 624.

The OC-M/STS-M interface 618 is operational to receive ATM cells fromthe AAL 616 and to transmit the ATM cells over the connection to thecommunication device 626. The OC-M/STS-M interface 618 also may receiveATM cells in the OC or STS format and transmit them to the AAL 616.

Call signaling may be received through and transferred from theOC-N/STS-N interface 606 and the ISDN/GR-303 interface 620. Also, callsignaling may be received through and transferred from the OC-M/STS-Minterface 618. The call signaling may be connected on a connection ortransmitted to the control interface directly or via another interfaceas explained above.

The AAL 616 comprises both a convergence sublayer and a segmentation andreassembly (SAR) sublayer. The AAL 616 obtains the identity of the DS0and the ATM VP/VC from the control interface 604. The AAL 616 isoperational to convert between the DS0 format and the ATM format.

If desired, the AAL 616 can be configured to accept control messagesthrough the control interface 604 for Nx64 calls. The ATM interworkingunit 602 is able to interwork, multiplex, and demultiplex for multipleDS0s.

DS0 connections are bi-directional and ATM connections are typicallyuni-directional. As a result, two virtual connections in opposingdirections typically will be required for each DS0. Those skilled in theart will appreciate how this can be accomplished in the context of theinvention. For example, the cross-connect can be provisioned with asecond set of VP/VCs in the opposite direction as the original set ofVP/VCs.

In some embodiments, it may be desirable to incorporate digital signalprocessing capabilities at the DS0 level. It may also be desired toapply echo control to selected DS0 circuits. In these embodiments, asignal processor 614 is included either separately (as shown) or as apart of the DS0 interface 612. The signaling processor 622 is configuredto send control messages to the ATM interworking unit 602 to implementparticular features on particular DS0 circuits. Alternatively, lookuptables may be used to implement particular features for particularcircuits or VP/VCs.

FIG. 7 illustrates another exemplary embodiment of an interworking unitwhich is an ATM interworking unit 702 suitable for the present inventionfor use with an SDH system. The ATM interworking unit 702 preferably hasa control interface 704, an STM-N electrical/optical (E/0) interface706, an E3 interface 708, an E1 interface 710, an E0 interface 712, asignal processor 714, an AAL 716, an STM-M electrical/optical (E/0)interface 718, and a DPNSS interface 720. As used herein in conjunctionwith STM, “N” refers to an integer, and “M” refers to an integer.

The control interface 704 receives control messages from the signalingprocessor 722, identifies E0 and virtual connection assignments in thecontrol messages, and provides these assignments to the AAL 716 forimplementation. The control messages are received over an ATM virtualconnection and through the STM-M interface 718 to the control interface604 or directly through the control interface from a link.

The STM-N E/O interface 706, the E3 interface 708, the El interface 710,the E0 interface 712, and the DPNSS interface 720 each can receive usercommunications from a second communication device 724. Likewise, theSTM-M E/O interface 718 can receive user communications from a thirdcommunication device 726.

The STM-N E/O interface 706 receives STM-N electrical or opticalformatted user communications and converts the user communications fromthe STM-N electrical or STM-N optical format to the E3 format. The E3interface 708 receives user communications in the E3 format anddemultiplexes the user communications to the E1 format. The E3 interface708 can receive E3s from the STM-N E/O interface 706 or from an externalconnection. The E1 interface 710 receives the user communications in theE1 format and demultiplexes the user communications to the E0 format.The E1 interface 710 receives E1s from the STM-N E/O interface 706 orthe E3 interface 708 or from an external connection. The E0 interface712 receives user communications in the E0 format and provides aninterface to the AAL 716. The DPNSS interface 720 receives usercommunications in the DPNSS format and converts the user communicationsto the E0 format. In addition, each interface may transmit usercommunications in a like manner to the communication device 724.

The STM-M E/O interface 718 is operational to receive ATM cells from theAAL 716 and to transmit the ATM cells over the connection to thecommunication device 726. The STM-M E/O interface 718 may also receiveATM cells in the STM-M E/O format and transmit them to the AAL 716.

Call signaling may be received through and transferred from the STM-NE/O interface 706 and the DPNSS interface 720. Also, call signaling maybe received through and transferred from the STM-M E/O interface 718.The call signaling may be connected on a connection or transmitted tothe control interface directly or via another interface as explainedabove.

The AAL 716 comprises both a convergence sublayer and a segmentation andreassembly (SAR) sublayer. The AAL obtains the identity of the E0 andthe ATM VP/VC from the control interface 704. The AAL 716 is operationalto convert between the E0 format and the ATM format, either in responseto a control instruction or without a control instruction. AAL's areknown in the art. If desired, the AAL 716 can be configured to receivecontrol messages through the control interface 704 for Nx64 usercommunications.

E0 connections are bi-directional and ATM connections typically areuni-directional. As a result, two virtual connections in opposingdirections typically will be required for each E0. Those skilled in theart will appreciate how this can be accomplished in the context of theinvention.

In some instances, it may be desirable to incorporate digital signalprocessing capabilities at the E0 level. Also, it may be desirable toapply echo control. In these embodiments, a signal processor 714 isincluded either separately (as shown) or as a part of the E0 interface712. The signaling processor 722 is configured to send control messagesto the ATM interworking unit 702 to implement particular features onparticular circuits. Alternatively, lookup tables may be used toimplement particular features for particular circuits or VP/VCs.

The Signaling Processor

The signaling processor receives and processes telecommunications callsignaling, control messages, and customer data to select connectionsthat establish communication paths for calls. In the preferredembodiment, the signaling processor processes SS7 signaling to selectconnections for a call. An example of call processing in a callprocessor and the associated maintenance that is performed for callprocessing is described in a U.S. patent application Ser. No. 09/026,766entitled “System and Method for Treating a Call for Call Processing,”which is incorporated herein by reference.

In addition to selecting connections, the signaling processor performsmany other functions in the context of call processing. It not only cancontrol routing and select the actual connections, but it also canvalidate callers, control echo cancellers, generate accountinginformation, invoke intelligent network functions, access remotedatabases, manage traffic, and balance network loads. One skilled in theart will appreciate how the signaling processor described below can beadapted to operate in the above embodiments.

FIG. 8 depicts an embodiment of a signaling processor. Other versionsalso are contemplated. In the embodiment of FIG. 8, the, signalingprocessor 802 has a signaling interface 804, a call processing controlsystem 806 (CPCS), and a call processor 808. It will be appreciated thatthe signaling processor 802 may be constructed as modules in a singleunit or as multiple units.

The signaling interface 804 is coupled externally to signalingsystems—preferably to signaling systems having a message transfer part(MTP), an ISDN user part (ISUP), a signaling connection control part(SCCP), an intelligent network application part (INAP), and atransaction capabilities application part (TCAP). The signalinginterface 804 preferably is a platform that comprises an MTP level 1810, an MTP level 2 812, an MTP level 3 814, an SCCP process 816, anISUP process 818, and a TCAP process 820. The signaling interface 804also has INAP functionality.

The signaling interface 804 may be linked to a communication device (notshown). For example, the communication device may be an SCP which isqueried by the signaling interface with a TCAP query to obtainadditional call-associated data. The answer message may have additionalinformation parameters that are required to complete call processing.The communication device also may be an STP or other device.

The signaling interface 804 is operational to transmit, process, andreceive call signaling. The TCAP, SCCP, ISUP, and INAP functionality usethe services of the MTP to transmit and receive the messages.Preferably, the signaling interface 804 transmits and receives SS7messages for MTP, TCAP, SCCP, and ISUP. Together, this functionality isreferred to as an “SS7 stack,” and it is well known. The softwarerequired by one skilled in the art to configure an SS7 stack iscommercially available. One example is the OMNI SS7 stack from Dale,Gesek, McWilliams & Sheridan, Inc. (the DGM&S company).

The processes of the signaling interface 804 process information that isreceived in message signal units (MSUs) and convert the information tocall information elements that are sent to the call processor 808 to beprocessed. A call information element may be, for example, an ISUP IAMmessage parameter from the MSU. The signaling interface 804 strips theunneeded header information from the MSU to isolate the messageinformation parameters and passes the parameters to the call processor808 as the call information elements. Examples of these parameters arethe called number, the calling number, and user service information.Other examples of messages with information elements are an ANM, an ACM,an REL, an RLC, and an INF. In addition, call information elements aretransferred from the call processor 808 back to the signaling interface804, and the information elements are reassembled into MSUs andtransferred to a signaling point.

The CPCS 806 is a management and administration system. The CPCS 806 isthe user interface and external systems interface into the callprocessor 808. The CPCS 806 serves as a collection point forcall-associated data such as logs, operational measurement data,statistical information, accounting information, and other call data.The CPCS 806 can configure the call-associated data and/or transmit itto reporting centers.

The CPCS 806 accepts data, such as the translations, from a source suchas an operations system and updates the data in the tables in the callprocessor 808. The CPCS 806 ensures that this data is in the correctformat prior to transferring the data to the call processor 808. TheCPCS 806 also provides configuration data to other devices including thecall processor 808, the signaling interface 804, the interworking unit(not shown), and the controllable ATM matrix (not shown). In addition,the CPCS 806 provides for remote control of call monitoring and calltapping applications from the call processor 808.

The CPCS 806 also serves as a collection point for alarms. Alarminformation is transferred to the CPCS 806. The CPCS 806 then transportsalarm messages to the required communication device. For example, theCPCS 806 can transport alarms to an operations center.

The CPCS 806 also has a human-machine interface (HMI). This allows aperson to log onto the CPCS 806 and manage data tables or review datatables in the CPCS or provide maintenance services.

The call processor 808 processes call signaling and controls an ATMinterworking unit, such as an ATM interworking multiplexer (mux) thatperforms interworking of DS0s and VP/VCs, and an ATM matrix. However,the call processor 808 may control other communications devices andconnections in other embodiments.

The call processor 808 comprises a control platform 822 and anapplication platform 824. Each platform 822 and 824 is coupled to theother platform.

The control platform 822 is comprised of various external interfacesincluding an interworking unit interface, a controllable ATM matrix, anecho interface, a resource control interface, a call informationinterface, and an operations interface. The control platform 822 isexternally coupled to an interworking unit control, a controllable ATMmatrix control, an echo control, a resource control, accounting, andoperations. The interworking unit interface exchanges messages with atleast one interworking unit. These messages comprise DS0 to VP/VCassignments, acknowledgments, and status information. The controllableATM matrix interface exchanges messages with at least one controllableATM matrix. These messages comprise DS0 to VP/VC assignments, VP/VC toVP/VC assignments, acknowledgments, and status information. The echocontrol interface exchanges messages with echo control systems. Messagesexchanged with echo control systems right include instructions to enableor disable echo cancellation on particular DS0s, acknowledgments, andstatus information.

The resource control interface exchanges messages with externalresources. Examples of such resources are devices that implementcontinuity testing, encryption, compression, tonedetection/transrnission, voice detection, and voice messaging. Themessages exchanged with resources are instructions to apply the resourceto particular DS0s, acknowledgments, and status information. Forexample, a message may instruct a continuity testing resource to providea loopback or to send and detect a tone for a continuity test.

The call information interface transfers pertinent call information to acall information processing system, such as to the CPCS 806. Typicalcall information includes accounting information, such as the parties tothe call, time points for the call, and any special features applied tothe call. One skilled in the art will appreciate how to produce thesoftware for the interfaces in the control platform 822.

The application platform 824 processes signaling information from thesignaling interface 804 to select connections. The identity of theselected connections are provided to the control platform 822 for theinterworking unit interface and/or for the controllable ATM matrixinterface. The application platform 824 is responsible for validation,translation, routing, call control, exceptions, screening, and errorhandling. In addition to providing the control requirements for theinterworking unit and the controllable ATM matrix, the applicationplatform 824 also provides requirements for echo control and resourcecontrol to the appropriate interface of the control platform 822. Inaddition, the application platform 824 generates signaling informationfor transmission by the signaling interface 804. The signalinginformation might be for ISUP, INAP, or TCAP messages to externalnetwork elements. Pertinent information for each call is stored in anenhanced circuit data block (ECDB) for the call. The ECDB can be usedfor tracking and accounting the call.

The application platform 824 preferably operates in general accord withthe Basic Call State Model (BCSM) defined by the ITU. An instance of theBCSM is created to handle each call. The BCSM includes an originatingprocess and a terminating process. The application platform 824 includesa service switching function (SSF) that is used to invoke the servicecontrol function (SCF). Typically, the SCF is contained in an SCP. TheSCF is queried with TCAP or INAP messages that are transported by thesignaling interface 804 and which are initiated with information fromthe SSF in the application platform 824. The originating or terminatingprocesses will access remote databases with intelligent network (IN)functionality via the SSF.

Software requirements for the application platform 824 can be producedin specification and description language (SDL) defined in ITU-T Z.100or similar logic or description languages. The SDL can be converted intoC code. A real time case tool such as SDT from Telelogic, Inc. or ObjectTime from Object Time, Inc. can be used. Additional C and C++ code canbe added as required to establish the environment. It will beappreciated that other software languages and tools may be used.

The call processor 808 can be comprised of the above-described softwareloaded onto a computer. The computer can be a generally availablefault-tolerant Unix computer, such as those provided by Sun, Tandem, orHewlett Packard. It may be desirable to utilize the multi-threadingcapability of a Unix operating system.

From FIG. 8, it can be seen that the application platform 824 processessignaling information to control numerous systems and facilitate callconnections and services. The SS7 signaling is exchanged between thecall processor 808 and external components through the signalinginterface 804, and control information is exchanged with externalsystems through the control platform 822. Advantageously, the signalinginterface 804, the CPCS 806, and the call processor 808 are notintegrated into a switch central processing unit (CPU) that is coupledto a switching matrix. Unlike an SCP, the components of the signalingprocessor 802 are capable of processing ISUP messages independently ofTCAP queries.

SS7 Message Destinations

SS7 messages are well known. Designations for various SS7 messagescommonly are used. Those skilled in the art are familiar with thefollowing message designations:

-   -   ACM—Address Complete Message    -   ANM—Answer Message    -   BLO—Blocking    -   BLA—Blocking Acknowledgment    -   CPG—Call Progress    -   CGB—Circuit Group Blocking    -   CGBA—Circuit Group Blocking Acknowledgment    -   GRS—Circuit Group Reset    -   GRA—Circuit Group Reset Acknowledgment    -   CGU—Circuit Group Unblocking    -   CGUA—Circuit Group Unblocking Acknowledgment    -   CQM—Circuit Group Query    -   CQR—Circuit Group Query Response    -   CRM—Circuit Reservation Message    -   CRA—Circuit Reservation Acknowledgment    -   CVT—Circuit Validation Test    -   CVR—Circuit Validation Response    -   CFN—Confusion    -   COT—Continuity    -   CCR—Continuity Check Request    -   EXM—Exit Message    -   INF—Information    -   INR—Information Request    -   IAM—Initial Address Message    -   LPA—Loop Back Acknowledgment    -   PAM—Pass Along Message    -   REL—Release    -   RLC—Release Complete    -   RSC—Reset Circuit    -   RES—Resume    -   SUS—Suspend    -   UBL—Unblocking    -   UBA—Unblocking Acknowledgment    -   UCIC—Unequipped Circuit Identification Code.        Call Processor Tables

Call processing typically entails two aspects. First, an incoming or“originating” connection is recognized by an originating call process.For example, the initial connection that a call uses to enter a networkis the originating connection in that network. Second, an outgoing or“terminating” connection is selected by a terminating call process. Forexample, the terminating connection is coupled to the originatingconnection in order to extend the call through the network. These twoaspects of call processing are referred to as the originating side ofthe call and the terminating side of the call.

FIG. 9 depicts an exemplary data structure preferably used by the callprocessor 802 of FIG. 8 to execute the BCSM. This is accomplishedthrough a series of tables that point to one another in various ways.The pointers typically are comprised of next function and next labeldesignations. The next function points to the next table, and the nextlabel points to an entry or a range of entries in that table. It will beappreciated that the pointers for the main call processing areillustrated in FIG. 9.

The primary data structure has a TDM trunk circuit table 902, an ATMtrunk circuit table 904, a trunk group table 906, a carrier table 908,an exception table 910, an originating line information (OLI) table 912,an automatic number identification (ANI) table 914, a called numberscreening table 916, a called number table 918, a routing table 920, atrunk group class of service (COS) table 922, and a message mappingtable 924. Also included in the data structure are a day of year table926, a day of week table 928, a time of day table 930, and a time zonetable 932.

The TDM trunk circuit table 902 contains information required toprovision the TDM side of a connection from the call processor site.Each circuit on the TDM side of a connection has an entry. The TDM trunkcircuit table 902 is accessed from the trunk group table 906 or anexternal call process, and it points to the trunk group table.

The ATM trunk circuit table 904 contains information required toprovision the ATM side of a connection. Typically, one record appears inthis table per ATM trunk group. Although, the system can be configuredalternately for multiple records per trunk group. The ATM trunk circuittable 904 is accessed from the trunk group table 906 or an external callprocess, and it points to the trunk group table.

The trunk group table 906 contains information that is required to buildtrunk groups out of different trunk members identified in the TDM andATM trunk circuit tables 902 and 904. The trunk group table 906 containsinformation related to the originating and terminating trunk groups. Thetrunk group table 906 typically points to the carrier table 908.Although, the trunk group table 906 may point to the exception table910, the OLI table 912, the ANI table 914, the called number screeningtable 916, the called number table 918, the routing table 920, the dayof year table 926, the day of week table 928, the time of day table 930,and the treatment table (see FIG. 10).

For default processing of an IAM of an outgoing call in the forwarddirection, when the call process determines call setup and routingparameters for user communications on the originating portion, the trunkgroup table 906 is the next table after the TDM and ATM trunk circuittables 902 and 904, and the trunk group table points to the carriertable 908. For default processing of an IAM of an outgoing call in theforward direction, when the call process determines call setup androuting parameters for user communications on the terminating portion,the trunk group table 906 is the next table after the routing table 920,and the trunk group table points to the TDM or ATM trunk circuit table902 or 904. For default processing of an ACM or an ANM of an outgoingcall in the originating direction, when the call process determinesparameters for signaling, the trunk group table 906 is the next tableafter the TDM or ATM trunk circuit table 902 or 904, and the trunk grouptable points to the message mapping table 924. It will be appreciatedthat this is the default method, and, as explained herein, otherimplementations of table processing occur.

The carrier table 908 contains information that allows calls to bescreened based, at least in part, on the carrier information parameterand the carrier selection parameter. The carrier table 908 typicallypoints to the exception table 910. Although, the carrier table 908 maypoint to the OLI table 912, the ANI table 914, the called numberscreening table 916, the called number table 918, the routing table 920,the day of year table 926, the day of week table 928, the time of daytable 930, the treatment table (see FIG. 10), and the database servicestable (see FIG. 11).

The exception table 910 is used to identify various exception conditionsrelated to the call that may influence the routing or handling of thecall. The exception table 910 contains information that allows calls tobe screened based, at least in part, on the called party number and thecalling party's category. The exception table 910 typically points tothe OLI table 912. Although, the exception table 910 can point to theANI table 914, the called number screening table 916, the called numbertable 918, the routing table 920, the day of year table 926, the day ofweek table 928, the time of day table 930, the call rate table, thepercent control table, the treatment table (see FIG. 10), and thedatabase services table (see FIG. 11).

The OLI table 912 contains information that allows calls to be screenedbased, at least in part, on originating line information in an IAM. TheOLI table 912 typically points to the ANI table 914. Although, the OLItable can point to the called number screening table 916, the callednumber table 918, the routing table 920, the day of year table 926, theday of week table 928, the time of day table 930, and the treatmenttable (see FIG. 10).

The ANI table 914 is used to identify any special characteristicsrelated to the caller's number, which is commonly known as automaticnumber identification. The ANI table 914 is used to screen and validatean incoming ANI. ANI specific requirements such as queuing, echocancellation, time zone, and treatments can be established. The ANItable 914 typically points to the called number screening table 916.Although, the ANI table 914 can point to the called number table 918,the routing table 920, the day of year table 926, the day of week table928, the time of day table 930, and the treatment table (see. FIG. 10).

The called number screening table 916 is used to screen called numbers.The called number screening table 916 determines the disposition of thecalled number and the nature of the called number. The called numberscreening table 916 is used to provide the trigger detection point (TDP)for an AIN SCP TCAP query. It is used, for example, with the localnumber portability (LNP) feature. The called number screening table caninvoke a TCAP. The called number screening table 916 typically points tothe called number table 918. Although, the called number screening table916 can point to the routing table 920, the treatment table, the callrate table, the percent table (see FIG. 10), and the database servicestable (see FIG. 11).

The called number table 918 is used to identify routing requirementsbased on, for example, the called number. This will be the case forstandard calls. The called number table 918 typically points to therouting table 910. In addition, the called number table 926 can beconfigured to alternately point to the day of year table 926. The callednumber table 918 can also point to the treatment table (see FIG. 10) andthe database services table (see FIG. 11).

The routing table 920 contains information relating to the routing of acall for various connections. The routing table 920 typically points tothe treatment table (see FIG. 10). Although, the routing table also canpoint to the trunk group table 906 and the database services table (seeFIG. 11).

For default processing of an IAM of an outgoing call in the forwarddirection, when the call process determines call setup and routingparameters for user communications, the routing table 920 is the nexttable after the called number table 918, and the routine table points tothe trunk group table 906. For default processing of an IAM of anoutgoing call in the forward direction, when the call process determinesparameters for signaling, the routing table 920 is the next table afterthe called number table 918, and the routing table points to the messagemapping table 924. It will be appreciated that this is the defaultmethod, and, as explained herein, other implementations of tableprocessing occur.

The trunk group COS table 922 contains information that allows calls tobe routed differently based on the class of service assigned to theoriginating trunk group and to the terminating trunk group. The trunkgroup COS table can point to the routing table 920 or the treatmenttable (see FIG. 10).

When the trunk group COS table 922 is used in processing, after therouting table 920 and the trunk group table 906 are processed, the trunkgroup table points to the trunk group COS table. The trunk group COStable points back to the routing table 920 for further processing.Processing then continues with the routing table 920 which points to thetrunk group table 906, and the trunk group table which points to the TDMor ATM trunk circuit table 902 or 904. It will be appreciated that thisis the default method, and, as explained herein, other implementationsof table processing occur.

The message mapping table 924 is used to provide instructions for theformatting of signaling messages from the call processor. It typicallycan be accessed by the routing table 920 or the trunk group table 906and typically determines the format of the outgoing messages leaving thecall processor.

The day of year table 926 contains information that allows calls to berouted differently based on the day of the year. The day of year tabletypically points to the routing table 920 and references the time zonetable 932 for information. The day of year table 926 also can point tothe called number screening table 916, the called number table 918, therouting table 920, the day of week table 928, the time of day table 930,and the treatment table (see FIG. 10).

The day of week table 928 contains information that allows calls to berouted differently based on the day of the week. The day of week tabletypically points to the routing table 920 and references the time zonetable 932 for information. The day of week table 928 also can point tothe called number screening table 916, the called number table 918, thetime of day table 930, and the treatment table (see FIG. 10).

The time of day table 930 contains information that allows calls to berouted differently based on the time of the day. The time of day table930 typically points to the routing table 920 and references the timezone table 932 for information. The time of day table 930 also can pointto the called number screening table 916, the called number table 918,and the treatment table (see FIG. 10).

The time zone table 932 contains information that allows call processingto determine if the time associated with the call processing should beoffset based on the time zone or daylight savings time. The time zonetable 932 is referenced by, and provides information to, the day of yeartable 926, the day of week table 928, and the time of day table 930.

FIG. 10 is an overlay of FIG. 9. The tables from FIG. 9 are present.However, for clarity, the table's pointers have been omitted, and sometables have not been duplicated in FIG. 10. FIG. 10 illustratesadditional tables that can be accessed from the tables of FIG. 9. Theseinclude an outgoing release table 1002, a treatment table 1004, a callrate table 1006, and a percent control table 1008, and time/date tables1010.

The outgoing release table 1002 contains information that allows callprocessing to determine how an outgoing release message is to beformatted. The outgoing release table 1002 typically points to thetreatment table 1006.

The treatment table 1004 identifies various special actions to be takenin the course of call processing. For example, based on the incomingtrunk group or ANI, different treatments or cause codes are used toconvey problems to the called and calling parties. This typically willresult in the transmission of a release message (REL) and a cause value.The treatment table 1004 typically points to the outgoing release table1002 and the database services table (see FIG. 11).

The call rate table 1006 contains information that is used to controlcall attempts on an attempt per second basis. Preferably, attempts from100 per second to 1 per minute are programmable. The call rate table1006 typically points to the called number screening table 916, thecalled number table 918, the routing table 920, and the treatment table1004.

The percent control table 1008 contains information that is used tocontrol call attempts based upon a percent value of the traffic that isprocessed through call processing. The percent control table 1008typically points to the called number screening table 916, the callednumber table 918, the routing table 920, and the treatment table 1004.

The date/time tables 1010 have been identified in FIG. 9 as the day ofyear table 926, the day of week table 928, the time of day table 926,and the time zone table 932. They are illustrated in FIG. 10 as a singlelocation for ease and clarity but need not be so located.

FIG. 11 is an overlay of FIGS. 9-10. The tables from FIGS. 9-10 arepresent. However, for clarity, the table's pointers have been omitted,and some tables have not been duplicated in FIG. 11.

FIG. 11 illustrates additional tables that can be accessed from thetables of FIGS. 9-10 and which are directed to the TCAP and the SCCPmessage processes. These include a database services table 1102, asignaling connection control part (SCCP) table 1104, an intermediatesignaling network identification (ISNI) table 1106, a transactioncapabilities application part (TCAP) table 1108, and an advancedintelligent network (AIN) event parameters table 1110.

The database services table 1102 contains information about the type ofdatabase service requested by call processing. The database servicestable 1102 references and obtains information from the SCCP table 1104and the TCAP table 1108. After the database function is performed, thecall is returned to normal call processing. The database services table1102 points to the called number table 918.

The SCCP table 1104 contains information and parameters required tobuild an SCCP message. The SCCP table 1104 is referenced by the databaseservices table 1102 and provides information to the database servicestable.

The ISNI table 1106 contains network information that is used forrouting SCCP message to a destination node. The ISNI table 1106 isreferenced by the SCCP table 1104 and provides information to the SCCPtable.

The TCAP table 1108 contains information and parameters required tobuild a TCAP message. The TCAP table 1108 is referenced by the databaseservices table 1102 and provides information to the database servicestable.

The AIN event parameters table 1110 contains information and parametersthat are included in the parameters portion of a TCAP event message. TheAIN event parameters table 1110 is referenced by the TCAP table 1108 andprovides information to the TCAP table.

FIG. 12 is an overlay of FIGS. 9-11. The tables from FIGS. 9-11 arepresent. However, for clarity, the tables have not been duplicated inFIG. 12. FIG. 12 illustrates additional tables that can be used to setupthe call process so that the tables of FIGS. 9-11 may be used. Thesesetup tables 1202 include a site office table 1204, an external echocanceller table 1206, an interworking unit (TWU) table 1208, acontrollable ATM matrix (CAM) interface table 1210, and a controllableATM matrix (CAM) table 1212.

The site office table 1204 contains information which lists office-wideparameters, some of which are information-based and others which affectcall processing. The site office table 1204 provides information to thecall processor or switch during initialization or other setupprocedures, such as population of data or transfer of information to oneor more memory locations for use during call processing.

The external echo canceller 1206 contains information that provides theinterface identifier and the echo canceller type when an external echocanceller is required. The external echo canceller table 1206 providesinformation to the call processor or switch during initialization orother setup procedures, such as population of data or transfer ofinformation to one or more memory locations for use during callprocessing.

The IWU table 1208 contains the internet protocol (IP) identificationnumbers for interfaces to the interworking units at the call processoror switch site. The IWU table 1208 provides information to the callprocessor or switch during initialization or other setup procedures,such as population of data or transfer of information to one or morememory locations for use during call processing.

The CAM interface table 1210 contains information for the logicalinterfaces associated with the CAM. The CAM interface table 1210provides information to the call processor or switch duringinitialization or other setup procedures, such as population of data ortransfer of information to one or more memory locations for use duringcall processing.

The CAM table 1212 contains information associated with the logical andphysical setup properties of the CAM. The CAM table 1212 providesinformation to the call processor or switch during initialization orother setup procedures, such as population of data or transfer ofinformation to one or more memory locations for use during callprocessing.

FIGS. 13-42 depict examples of the various tables described above. Itwill be appreciated that other versions of tables may be used. Inaddition, information from the identified tables may be combined orchanged to form different tables.

FIG. 13 depicts an example of a TDM trunk circuit table. The TDM trunkcircuit table is used to access information about the originatingcircuit for originating circuit call processing. It also is used toprovide information about the terminating circuit for terminatingcircuit call processing. The trunk group number of the circuitassociated with the call is used to enter the table. The group member isthe second entry that is used as a key to identify or fill informationin the table. The group member. identifies the member number of thetrunk group to which the circuit is assigned, and it is used for thecircuit selection control.

The table also contains the trunk circuit identification code (TCIC).The TCIC identifies the trunk circuit which is typically a DS0. The echocanceller (EC) label entry identifies the echo canceller, if any, whichis connected to the circuit. The interworking unit (IWU) label and theinterworking unit (IWU) port identify the hardware location and the portnumber, respectively, of the interworking unit. The DS1/E1 label and theDS1/E1 channel denote the DS1 or the E1 and the channel within the DS1or E1, respectively, that contains the circuit. The initial statespecifies the state of the circuit when it is installed. Valid statesinclude blocked if the circuit is installed and blocked from usage,unequipped if the circuit is reserved, and normal if the circuit isinstalled and available from usage.

FIG. 14 depicts an example of an ATM trunk circuit table. The ATM trunkcircuit table is used to access information about the originatingcircuit for originating circuit call processing. It also is used toprovide information about the terminating circuit for terminatingcircuit call processing.

The trunk group number of the circuit associated with the call is usedto enter the table. The group size denotes the number of members in thetrunk group. The starting trunk circuit identification code (TCIC) isthe starting TCIC for the trunk group, and it is used in the routinglabel of an ISUP message. The transmit interface label identifies thehardware location of the virtual path on which the call will betransmitted. The transmit interface label may designate either aninterworking unit interface or a CAM interface for the designated trunkmembers. The transmit virtual path identifier (VPI) is the VP that willbe used on the transmission circuit side of the call. The receiveinterface label identifies the hardware location of the virtual path onwhich the call will be received. The receive interface label maydesignate either an interworking unit interface or a CAM interface forthe designated trunk members. The receive virtual path identifier (VPI)is the VP that will be used on the reception circuit side of the call.The initial state specifies the state of the circuit when it isinstalled. Valid states include blocked if the circuit is installed andblocked from usage, unequipped if the circuit is reserved, and normal ifthe circuit is installed and available from usage.

FIG. 15A depicts an example of a trunk group table. The trunk groupnumber of the trunk group associated with the circuit is used to keyinto the trunk group table. The administration information field is usedfor information purposes concerning the trunk group and typically is notused in call processing. The associated point code is the point code forthe far end switch or call processor to which the trunk group isconnected. The common language location identifier (CLLI) entry is astandardized Bellcore entry for the associated office to which the trunkgroup is connected. The trunk type identifies the type of the trunk inthe trunk group. The trunk type may be a TDM trunk, an ATM trunk fromthe interworking unit, or an ATM trunk from the CAM.

The associated numbering plan area (NPA) contains informationidentifying the switch from which the trunk group is originating or towhich the trunk group is terminating. The associated jurisdictioninformation parameter (JIP) contains information identifying the switchfrom which the trunk group is originating or to which the trunk group isterminating. If an ISUP JIP is not received in an IAM, the default JIPis a value recorded on the call processor ECDB. If an incoming IAM doesnot have a JIP, call processing will populate the JIP of the outgoingIAM with the default value from the trunk group table. If a JIP is notdata filled, an outgoing JIP is not transmitted.

The time zone label identifies the time zone that should be used whencomputing a local date and a local time for use with a day of yeartable, the day of week table, and the time of day table. The echocanceller information field describes the trunk group echo cancellationrequirements. Valid entries for the echo canceller information includenormal for a trunk group that uses internal echo cancellation, externalfor a trunk group that requires external echo cancellers, and disablefor a trunk group that requires no echo cancellation for any callpassing over the group.

FIG. 15B is a continuation of FIG. 15A for the trunk group table. Thesatellite entry specifies that the trunk group for the circuit isconnected through a satellite. If the trunk group uses too manysatellites, then a call should not use the identified trunk group. Thisfield is used in conjunction with the nature of connection satelliteindicator field from the incoming IAM to determine if the outgoing callcan be connected over this trunk group. The select sequence indicatesthe methodology that will be used to select a connection. Valid entriesfor the select sequence field include the following: most idle, leastidle, ascending, or descending. The interworking unit (IWU) prioritysignifies that outgoing calls will attempt to use a trunk circuit on thesame interworking unit before using a trunk circuit on a differentinterworking unit.

Glare resolution indicates how a glare situation is to be resolved.Glare is the dual seizure of the same circuit. If the glare resolutionentry is set to “even/odd,” the switch or the call processor with thehigher point code value will control the even number TCICs within thetrunk group. The switch or call processor with the lower point codevalue will control the odd number TCICs. If the glare resolution entryis set to “all,” the call processor controls all of the TCICs within thetrunk group. Yf the glare resolution entry is set to “none,” the callprocessor will have no glare control and will yield to all doubleseizures within the trunk group.

Continuity control indicates whether continuity is to be checked.Continuity for outgoing calls on the originating call processor arecontrolled on a trunk group basis. This field specifies whethercontinuity is not required or whether continuity is required and thefrequency of the required check. The field identifies a percentage ofthe calls that require continuity check.

The reattempt entry specifies how many times the outgoing call will bere-attempted using a different circuit from the same trunk group after acontinuity check failure, a glare, or other connection failure. Theignore local number portability (LNP) information specifies whether ornot the incoming LNP information is ignored. The treatment label is alabel into the treatment table for the trunk group used on the call.Because specific trunk group connections may require specific releasecauses or treatments for a specific customer, this field identifies thetype of treatment that is required. The message mapping label is a labelinto the message mapping table which specifies the backward messageconfiguration that will be used on the trunk group.

FIG. 15C is a continuation of FIG. 15B for the trunk group table. Thequeue entry signifies that the terminating part of the trunk group iscapable of queuing calls originating from a subscriber that called anumber which terminates in this trunk group. The ring no answer entryspecifies whether the trunk group requires ring no answer timing. If theentry is set to 0, the call processing will not use the ring no answertiming for calls terminated on the trunk group. A number other than 0specifies the ring no answer timing in seconds for calls terminating onthis trunk group. The voice path cut through entry identifies how andwhen the terminating call's voice path will be cut through on the trunkgroup. The options for this field include the following: connect for acut through in both directions after receipt of an ACM, answer for cutthrough in the backward direction upon receipt of an ACM, then cutthrough in the forward direction upon receipt of an ANM, or immediatefor cut through in both directions immediately after an IAM has beensent.

The originating class of service (COS) label provides a label into aclass of service table that determines how a call is handled based onthe combination of the originating COS and the terminating COS fromanother trunk group. Based on the combination of this field and theterminating COS of another trunk group's field, the call will be handleddifferently. For example, the call may be denied, route advanced, orotherwise processed. The terminating class of service (COS) labelprovides a label into a class of service table that determines how acall is handled based on the combination of the originating COS fromanother trunk group and the terminating COS from the present trunkgroup. Based on a combination of this field and the originating COS thecall will be handled differently. For example, the call may be denied,route advanced, or otherwise processed.

Call control provides an index to a specific trunk group level trafficmanagement control. Valid entries include normal for no control applied,slip control, applied wide area telecommunications service (WATS)reroute functionality, cancel control, reroute control overflow, andreroute immediate control. The next function points to the next table,and the next label points to an entry or a range of entries in thattable.

FIG. 16 depicts an example of a carrier table. The carrier label is thekey to enter the table. The carrier identification (ID) specifies thecarrier to be used by the calling party. The carrier selection entryidentifies how the caller specifies the carrier. For example, itidentifies whether the caller dialed a prefix digit or whether thecaller was pre-subscribed. The carrier selection is used to determinehow the call will be routed. The next function points to the next table,and the next label defines an area in that table for further callprocessing.

FIG. 17 depicts an example of an exception table. The exception label isused as a key to enter the table. The calling party's category entryspecifies how to process a call from an ordinary subscriber, an unknownsubscriber, or a test phone. The called number nature of addressdifferentiates between 0+calls, 1+calls, test calls, local routingnumber (LRN) calls, and international calls. For example, internationalcalls might be routed to a pre-selected international carrier. Thecalled number “digits from” and “digits to” focus further processingunique to a defined range of called numbers. The “digits from” field isa decimal number ranging from 1-15 digits. It can be any length and, iffilled with less than 15 digits, is filled with 0s for the remainingdigits. The “digits to” is a decimal number ranging from 1-15 digits. Itcan be any length and, if filled with less than 15 digits, is filledwith 9s for the remaining digits. The next function and next labelentries point to the next table and the next entry within that table forthe next routing function.

FIG. 18 depicts an example of the originating line information (OLI)table. The OLI label is used as a key to enter the table from a priornext function operation. The originating line information entryspecifies the information digits that are being transmitted from acarrier. Different calls are differentiated based on the informationdigits. For example, the information digits may identify an ordinarysubscriber, a multi-party line, NOD service, prison service, cellularservice, or private pay station. The next function and next labelentries point to the next table and the area within that table for thenext routing function.

FIG. 19 depicts an example of an automatic number identification (ANI)table. The ANI label is used as a key to enter the table from a priornext option. The charge calling party number “digits from” and “digitsto” focus further processing unique to ANI within a given range. Theseentries are looked at to determine if the incoming calling number fallswithin the “digits from” and “digits to” fields. The time zone labelindicates the entry in the time zone table that should be used whencomputing the local date and time. The time zone label overrides thetime zone information from the trunk group table 906.

The customer information entry specifies further customer information onthe originating side for call process routing. The echo cancellation(EC) information field specifies whether or not to apply echocancellation to the associated ANI. The queue entry identifies whetheror not queuing is available to the calling party if the called party isbusy. Queuing timers determine the length of time that a call can bequeued. The treatment label defines how a call will be treated based oninformation in the treatment table. For example, the treatment label maysend a call to a specific recording based on a dialed number. The nextfunction and next label point to the next table and an area within thattable for further call processing.

FIG. 20 depicts an example of a called number screening table. Thecalled number screening label is used as a key to enter the table. Thecalled number nature of address indicates the type of dialed number, forexample, national versus international. The nature of address entryallows the call process to route a call differently based on the natureof address value provided. The “digits from” and “digits to” entriesfocus further processing unique to a range of called numbers. The“digits from” and “digits to” columns both contain called number digits,such as NPA-NXX ranges, that may contain ported numbers and are checkedfor an LRN. This table serves as the trigger detection point (TDP) foran LNP TCAP when, for example, NPA-NXXs of donor switches that have hadsubscribers port their numbers are data filled in the “digits from” and“digits to” fields. The delete digits field provides the number ofdigits to be deleted from the called number before processing continues.The next function and next label point to the next table and the areawithin that table for further call processing.

FIG. 21 depicts an example of a called number table. The called numberlabel is used as a key to enter the table. The called number nature ofaddress entry indicates the type of dialed number, for example, nationalversus international. The “digits from” and “digits to” entries focusfurther processing unique to a range of numbers, including LRNs. Thenext function and next label point to a next table and the area withinthat table used for further call processing.

FIG. 22 depicts an example of a day of year table. The day of year labelis used as a key to enter the table. The date field indicates the localdate which is applicable to the action to be taken during the processingof this table. The next function and next label identify the table andthe area within that table for further call processing.

FIG. 23 depicts an example of a day of week table. The day of week labelis a key that is used to enter the table. The “day from” field indicatesthe local day of the week on which the action to be taken by this tableline entry is to start. The “day to” field indicates the local day ofthe week on which the action to be taken by this table line entry is toend. The next function and next label identify the next table and thearea within that table for further call processing.

FIG. 24 depicts an example of a time of day table. The time of day labelis used as a key to enter the table from a prior next function. The“time from” entry indicates the local time on which an action to betaken is to start. The “time to” field indicates the local time justbefore which the action to be taken is to stop. The next function andnext label entries identify the next table and the area within thattable for further call processing.

FIG. 25 depicts an example of a time zone table. The time zone label isused as a key to enter the table and to process an entry so that acustomer's local date and time may be computed. The coordinateduniversal time (UTC) indicates a standard offset of this time zone fromthe UTC. The UTC is also known as Greenwich mean time, GMT, or Zulu. TheUTC should be positive for time zones east of Greenwich, such as Europeand Asia, and negative for time zones west of Greenwich, such as NorthAmerica. The daylight savings entry indicates whether daylight savingstime is used during the summer in this time zone.

FIG. 26 depicts an example of a routing table. The routing label is usedas a key to enter the table from a prior next function. The route numberspecifies a route within a route list. Call processing will process theroute choices for a given route label in the order indicated by theroute numbers. The next function and next label identify the next tableand the area within that table for further call processing. The signalroute label is associated with the next action to be taken by callprocessing for this call. The signal route label provides the index toaccess the message mapping label. The signal route label is used inorder to modify parameter data fields in a signaling message that isbeing propagated to a next switch or a next call processor.

FIG. 27 depicts an example of a trunk group class of service (COS)table. The originating trunk COS label and the terminating trunk COSlabel are used as keys to enter the table and define call processing.The next function identifies the next action that will be taken by callprocessing for this call. Valid entries in the next function column maybe continued, treat, route advanced, or routing. Based on these entriescall processing may continue using the current trunk group, send thecalls to treatment, skip the current trunk group and the routing tableand go to the next trunk group on the list, or send the call to adifferent label in the routing table. The next label entry is a pointerthat defines the trunk circuit group that the next function will use toprocess the call. This field is ignored when the next function iscontinued or route advanced.

FIG. 28 depicts an example of a treatment table. The treatment label isa key that is used to enter the table. The treatment label is adesignation in a call process that determines the disposition of thecall. The error/cause label correspond either to internally generatederror conditions and call processing or to incoming release causevalues. For each treatment label, there will be a set of errorconditions and cause values to that will be associated with a series oflabels for the call processing error conditions and a series of labelsfor all incoming release message cause values. The next function andnext label point to the next table and the area within that table forfurther call processing.

FIG. 29 depicts an example of an outgoing release table. The outgoingrelease label is used as a key to enter the table for processing. Theoutgoing cause value location identifies the type of network to be used.For example, the location entry may specify a local or remote network ora private, transit, or international network. The coding standardidentifies the standard as an International Telecommunications Union(ITU) standard or an American National Standards Institute (ANSI)standard. The cause value designates error, maintenance, ornon-connection processes.

FIG. 30 depicts an example of a percent control table. The percent labelis used as a key to enter the table. The control percentage specifiesthe percentage of incoming calls that will be affected by the control.The control next function allows attempts for call connection to berouted to another table during call processing. The control next labelpoints to an area within that table for further call processing. Thepassed next function allows only incoming attempts to be routed toanother table. The next label points to an area in that table forfurther call processing.

FIG. 31 depicts an example of a call rate table. The call rate label isused as a key to enter the table. The call rate specifies the number ofcalls that will be passed by the control on or for completion. Callprocessing will use this information to determine if the incoming callnumber falls within this control. The control next function allows ablocked call attempt to be routed to another table. The control nextlabel is a pointer that defines the area in the next table for furthercall processing. The passed next function allows only an incoming callattempt to be rerouted to another table. The passed next function is apointer that defines an area in that table for further call processing.

FIG. 32 depicts an example of a database services table. The databaseservices label is used as a key to enter the table. The service typedetermines the type of logic that is applied when building andresponding to database queries. Service types include local numberportability and N00 number translation. The signaling connection controlpart (SCCP) label identifies a location within an SCCP table for furthercall processing. The transaction capabilities application part (TCAP)label identifies a location within a TCAP table for further processing.The next function identifies the location for the next routing functionbased on information contained in the database services table as well asinformation received from a database query. The next label entryspecifies an area within the table identified in the next function forfurther processing.

FIG. 33A depicts an example of a signaling connection control part(SCCP) table. The SCCP label is used as a key to enter the field. Themessage type entry identifies the type of message that will be sent inthe SCCP message. Message types include Unitdata messages and ExtendedUnitdata messages. The protocol class entry indicates the type ofprotocol class that will be used for the message specified in themessage type field. The protocol class is used for connectionlesstransactions to determine whether messages are discarded or returnedupon an error condition. The message handling field identifies how thedestination call processor or switch is to handle the SCCP message if itis received with errors. This field will designate that the message isto be discarded or returned. The hop counter entry denotes the number ofnodes through which the SCCP message can route before the message isreturned with an error condition. The segmentation entry denotes whetheror not this SCCP message will use segmentation and send more than oneSCCP message to the destination.

FIG. 33B is a continuation of FIG. 33A for the SCCP table. Theintermediate signaling network identification (ISNI) fields allow theSCCP message to traverse different networks in order to reach a desirednode. The ISNI type identifies the type of ISNI message format that willbe used for this SCCP message. The route indicator subfield identifieswhether or not this SCCP message requires a special type of routing togo through other networks. The mark identification subfield identifieswhether or not network identification will be used for this SCCPmessage. The label subfield identifies a unique address into the ISNItable when the route indicator sub-field is set to “constrained” and themark identification subfield is set to “yes.”

FIG. 33C is a continuation of FIG. 33B for the SCCP table. FIG. 33Cidentifies the called party address field and subfields to provideinformation on how to route this SCCP message. The address indicatorsubsystem number (SSN) indicates whether or not a subsystem number willbe included in the called party address. The point code entry indicateswhether or not a point code will be included in the calling partyaddress. The global title indicator subfield identifies whether or not aglobal title translation will be used to route the SCCP message. If aglobal title translation is chosen, this subfield also identifies thetype. The routing indicator subfield identifies the elements that willbe used to route the message. Valid entries include global title andpoint code. The national/international subfield identifies whether theSCCP message will use national or international routing and set up.

The subsystem number field identifies the subsystem number for the SCCPmessage. The point code number indicates the, destination point code towhich the SCCP message will be routed. This field will be used forrouting messages that do not require SCCP translation.

The global title translation field allows intermediate nodes totranslate SCCP messages so that the messages can be routed to thecorrect destination with the correct point code. The global titletranslation type entry directs the SCCP message to the correct globaltitle translation function. The encode scheme identifies how the addresstype will be encoded. The number plan subfield identifies the numberingplan that will be sent to the destination node. The address typesubfield will identify which address type to use for address digits andthe SCCP routing through the network.

FIG. 33D is a continuation of FIG. 33C for the SCCP table. FIG. 33Didentifies the calling party address field which contains the routinginformation that the destination database uses to retain the SCCPmessage. The address indicator subsystem number (SSN) indicates whetheror not a subsystem number will be included in the called party address.The point code subfield indicates whether or not a point code will beincluded in the calling party address. The global title indicatorsubfield identifies whether or not global title translation will be usedto route the SCCP message. The routing indicator subfield identifieswhich elements will be used throughout the message. This field mayinclude global title elements or point code elements. Thenational/international subfield identifies whether the SCCP will usenational or international routing and set up.

The subsystem number identifies a subsystem number for the SCCP message.The point code number field indicates the destination point code towhich the SCCP message will be routed. The global title translationsallow the intermediate nodes to translate SCCP messages and to route themessages to the correct destination. The global title translation typedirects the SCCP message to the correct global title translationfunction. The encode scheme identifies how the address type will beencoded. The number plan identifies the number plan that will be sent tothe destination node. The address type subfield identifies the addresstype to use for address digits in the SCCP routing through the network.

FIG. 34 depicts an example of an intermediate signaling networkidentification (ISNI) table. The ISNI table contains a list of networksthat will be used for routing SCCP messages to the destination node. TheISNI label is used as a key to enter the table. The network fields 1-16identify the network number of up to 16 networks that may be used forrouting the SCCP message.

FIG. 35 depicts an example of a transaction capabilities applicationpart (TCAP) table. The TCAP label is used as a key to enter the table.The TCAP type identifies the type of the TCAP that will be constructed.The TCAP types include advanced intelligent network (AIN) anddistributed intelligent network architecture (DINA). The tag classindicates whether the message will use a common or proprietarystructure. The package type field identifies the package type that willbe used in the transaction portion of the TCAP message. The componenttype field identifies the component type that will be used in thecomponent portion of the TCAP message. The message type field identifiesthe type of TCAP message. Message types include variable optionsdepending on whether they are AIN message types or DINA message types.

FIG. 36 depicts an example of an external echo canceller table. The echocanceller type specifies if an external echo canceller is being used onthe circuit and, if so, the type of echo canceller. The echo cancellerlabel points to a location in the controllable ATM matrix table forfurther call processing. The RS-232 address is the address of the RS-232interface that is used to communicate with the external echo canceller.The module entry is the module number of the external echo canceller.

FIG. 37 depicts an example of an interworking unit interface table. Theinterworking unit (IWU) is a key that is used to enter the table. TheIWU identification (ID) identifies which interworking unit is beingaddressed. The internet protocol (IP) sockets 1-4 specify the IP socketaddress of any of the four connections to the inter-working unit.

FIG. 38 depicts an example of a controllable ATM matrix (CAM) interfacetable. The CAM interface label is used as a key to enter the table. TheCAM label indicates which CAM contains the interface. The logicalinterface entry specifies a logical interface or port number in the CAM.

FIG. 39 depicts an example of a controllable ATM matrix (CAM) table. TheCAM label is used as a key to enter the table. The CAM type indicatesthe type of CAM control protocol. The CAM address identifies the addressof the CAM.

FIG. 40A depicts an example of a call processor or switch site officetable. The office CLLI name identifies a CLLI of the associated officefor the call processor or switch. The call processor or switch site nodeidentifier (ID) specifies the call processor or switch node identifier.The call processor or switch origination identifier (ID) specifies acall processor or switch origination identifier. The software identifier(ID) specifies a software release identifier. The call processoridentifier (ID) specifies the call processor or switch identifier thatis sent to the inter working units.

FIG. 40B is a continuation of FIG. 40A of the call processor or switchsite office table. The automatic congestion control (ACC) specifieswhether ACC is enabled or disabled. The automatic congestion controllevel (ACL) 1 onset identifies an onset percentage value of a firstbuffer utilization. The ACL 1 abate entry specifies an abatementpercentage of utilization for a first buffer. The ACL 2 onset entryspecifies an onset level for a second buffer. The ACL 2 abate entryspecifies an abatement level percentage of buffer utilization for asecond buffer. The ACL 3 onset entry specifies an onset level percentageof buffer utilization for a third buffer. The ACL 3 abate entryspecifies an abatement level percentage of buffer utilization for athird buffer.

FIG. 40C is a continuation of FIG. 40B for the call processor or switchsite office table. The maximum trunks for the off hook queuing (maxtrunks OHQ) specifies a maximum number of trunk groups that can have theoff hook queuing enabled. The OHQ timer one (TQ1) entry specifies thenumber of milliseconds for the off hook timer number one. The OHQ timertwo (TQ2) entry specifies the number of seconds for the off hook timernumber two. The ring no answer timer specifies the number of seconds forthe ring no answer timer. The billing active entry specifies whetherECDBs are being sent to the call processing control system (CPCS). Thenetwork management (NWM) allow entry identifies whether or not aselective trunk reservation and group control are allowed or disallowed.The billing failure free call entry specifies if a call will not bebilled if the billing process is unavailable. The billing failure freecall will either be enabled for free calls or disabled so that there areno free calls.

FIG. 40D is a continuation of FIG. 40C for the call processor or switchsite office table. The maximum (max) hop counts identifies the number ofcall processor or switch hops that may be made in a single call. Themaximum (max) table lookups identifies the number of table lookups thatmay performed for a single call. This value is used to detect loops inrouting tables.

FIGS. 41A-41B depict an example of an advanced intelligent network (AIN)event parameters table. The AIN event parameters table has two columns.The first identifies the parameters that will be included in theparameters portion of the TCAP event message. The second entry mayinclude information for analysis.

FIG. 42 depicts an example of a message mapping table. This table allowsthe call processor to alter information in outgoing messages. Themessage type field is used as a key to enter the table and representsthe outgoing standard message type. The parameters entry is a pertinentparameter within the outgoing message. The indexes point to variousentries in the trunk group and determine if parameters are passedunchanged, omitted, or modified in the outgoing messages.

Those skilled in the art will appreciate that variations from thespecific embodiments disclosed above are contemplated by the invention.The invention should not be restricted to the above embodiments, butshould be measured by the following claims.

1. A call processing system comprising: a signaling interface; a callprocessor coupled to the signaling interface; a service control databasecoupled to the call processor by one of a backplane, a bus, and amotherboard; an interworking unit coupled to the call processor; whereinthe signaling interface is configured to receive a signaling message fora call including signaling information and transfer the signalinginformation to the call processor; wherein the call processor isconfigured to process the signaling information to transfer a firstquery including the signaling information to the local database, whereinthe first query does not use a Signaling System Seven (SS7) protocol;wherein the local database is configured to process the first query totransfer a response including a call routing instruction to the callprocessor, wherein the response does not use the SS7 protocol; whereinthe call processor is configured to process the response to transfer acontrol message to the interworking unit; and wherein the interworkingunit is configured to interwork user communications for the call betweena Time Division Multiplex (TDM) communication format and a packetcommunication format in response to the control message.
 2. The callprocessing system of claim 1 wherein the signaling information comprisesan N00 number and the local database is configured to translate the N00number into a 10-digit telephone number, and wherein the call routinginstruction comprises the 10-digit telephone number.
 3. The callprocessing system of claim 1 wherein the signaling information comprisesa Virtual Private Network (VPN) number and the local database isconfigured to translate the VPN number into a 10-digit telephone number,and wherein the call routing instruction comprises the 10-digittelephone number.
 4. The call processing system of claim 1 wherein: thecall processor is configured to process the response to generate asecond query; the signaling interface is configured to transfer an SS7message including the second query, receive a second SS7 messageincluding additional signaling information, and transfer the additionalsignaling information to the call processor; and the call processor isconfigured to process the additional signaling information to transferthe control message to the interworking unit.
 5. The call processingsystem of claim 4 wherein the SS7 message is processed by a numberportability service control point to transfer the second SS7 messageincluding the additional signaling information.
 6. The call processingsystem of claim 1 wherein the packet communication format comprisesasynchronous transfer mode.
 7. The call processing system of claim 1wherein the local database comprises a local service control point.
 8. Acall processing system comprising: a signaling interface; a callprocessor coupled to the signaling interface; a service control databasecoupled to the call processor by one of a backplane, a bus, and amotherboard; an interworking unit coupled to the call processor; whereinthe signaling interface is configured to receive a first SignalingSystem Seven (SS7) message for a call including signaling informationand transfer the signaling information to the call processor; whereinthe call processor is configured to process the signaling information totransfer a first query including the signaling information to the localdatabase, wherein the first query does not use an SS7 protocol; whereinthe local database is configured to process the first query to transfera response including a call routing instruction to the call processor,wherein the response does not use the SS7 protocol; wherein the callprocessor is configured to process the response to transfer a controlmessage to the interworking unit; and wherein the interworking unit isconfigured to interwork user communications for the call between a TimeDivision Multiplex (TDM) communication format and a packet communicationformat in response to the control message.
 9. The call processing systemof claim 8 wherein the signaling information comprises an N00 number andthe local database is configured to translate the N00 number into a10-digit telephone number, and wherein the call routing instructioncomprises the 10-digit telephone number.
 10. The call processing systemof claim 8 wherein the signaling information comprises a Virtual PrivateNetwork (VPN) number and the local database is configured to translatethe VPN number into a 10-digit telephone number, and wherein the callrouting instruction comprises the 10-digit telephone number.
 11. Thecall processing system of claim 8 wherein: the call processor isconfigured to process the response to generate a second query; thesignaling interface is configured to transfer a second SS7 messageincluding the second query, receive a third SS7 message includingadditional signaling information, and transfer the additional signalinginformation to the call processor; and the call processor is configuredto process the additional signaling information to transfer the controlmessage to the interworking unit.
 12. The call processing system ofclaim 8 wherein the second SS7 message is processed by a numberportability service control point to transfer the third SS7 messageincluding the additional signaling information.
 13. The call processingsystem of claim 8 wherein the packet communication format comprisesasynchronous transfer mode.
 14. The call processing system of claim 8wherein the local database comprises a local service control point. 15.A method of operating a call processing system comprising a signalinginterface, a call processor coupled to the signaling interface, aservice control database, and an interworking unit coupled to the callprocessor, the method comprising: in the signaling interface, receivinga signaling message for a call including signaling information andtransferring the signaling information to the call processor; in thecall processor, processing the signaling information to transfer a firstquery including the signaling information to the local database, whereinthe first query does not use a Signaling System Seven (SS7) protocol,and wherein the service control database is coupled to the callprocessor by one of a backplane, a bus, and a motherboard; in the localdatabase, processing the first query to transfer a response including acall routing instruction to the call processor, wherein the responsedoes not use the SS7 protocol; in the call processor, processing theresponse to transfer a control message to the interworking unit; and inthe interworking unit, interworking user communications for the callbetween a Time Division Multiplex (TDM) communication format and apacket communication format in response to the control message.
 16. Themethod of claim 15 wherein the signaling information comprises an N00number and wherein, in the local database, processing the first query totransfer a response comprises translating the N00 number into a 10-digittelephone number, and wherein the call routing instruction comprises the10-digit telephone number.
 17. The method of claim 15 wherein thesignaling information comprises a Virtual Private Network (VPN) numberand wherein, in the local database, processing the first query totransfer a response comprises translating the VPN number into a 10-digittelephone number, and wherein the call routing instruction comprises the10-digit telephone number.
 18. The method of claim 15 wherein: in thecall processor, processing the response to transfer the control messageto the interworking unit comprises processing the response to generate asecond query; and further comprising in the signaling interface,transferring an SS7 message including the second query, receiving asecond SS7 message including additional signaling information, andtransferring the additional signaling information to the call processor;and wherein in the call processor, processing the response to transferthe control message to the interworking unit further comprisesprocessing the additional signaling information.
 19. The method of claim18 wherein the SS7 message is processed by a number portability servicecontrol point to transfer the second SS7 message including theadditional signaling information.
 20. The method of claim 15 wherein thepacket communication format comprises asynchronous transfer mode. 21.The method of claim 15 wherein the local database comprises a localservice control point.
 22. A method of operating a call processingsystem comprising a signaling interface, a call processor coupled to thesignaling interface, a service control database, and an interworkingunit coupled to the call processor, the method comprising: in thesignaling interface, receiving a first Signaling System Seven (SS7)message including signaling information and transferring the signalinginformation to the call processor; in the call processor, processing thesignaling information to transfer a first query including the signalinginformation to the local database, wherein the first query does not usea Signaling System Seven (SS7) protocol, and wherein the service controldatabase is coupled to the call processor by one of a backplane, a bus,and a motherboard; in the local database, processing the first query totransfer a response including a call routing instruction to the callprocessor, wherein the response does not use the SS7 protocol; in thecall processor, processing the response to transfer a control message tothe interworking unit; and in the interworking unit, interworking usercommunications for the call between a Time Division Multiplex (TDM)communication format and a packet communication format in response tothe control message.
 23. The method of claim 22 wherein the signalinginformation comprises an N00 number and wherein, in the local database,processing the first query to transfer a response comprises translatingthe N00 number into a 10-digit telephone number, and wherein the callrouting instruction comprises the 10-digit telephone number.
 24. Themethod of claim 22 wherein the signaling information comprises a VirtualPrivate Network (VPN) number and wherein, in the local database,processing the first query to transfer a response comprises translatingthe VPN number into a 10-digit telephone number, and wherein the callrouting instruction comprises the 10-digit telephone number;
 25. Themethod of claim 22 wherein: in the call processor, processing theresponse to transfer the control message to the interworking unitcomprises processing the response to generate a second query; andfurther comprising in the signaling interface, transferring a second SS7message including the second query, receiving a third SS7 messageincluding additional signaling information, and transferring theadditional signaling information to the call processor; and wherein inthe call processor, processing the response to transfer the controlmessage to the interworking unit further comprises processing theadditional signaling information to transfer the control message to theinterworking unit.
 26. The method of claim 25 wherein the second SS7message is processed by a number portability service control point totransfer the third SS7 message including the additional signalinginformation.
 27. The method of claim 22 wherein the packet communicationformat comprises asynchronous transfer mode.
 28. The method of claim 22wherein the local database comprises a local service control point.